An Explanation of the Restore Process
Being able to easily restore data is a core function of SyncBackSE. Here are some example scenarios of when you'll want to run a restore operation:
| · | You inadvertently delete a file and/or folder and need to recover it easily and quickly. |
| · | As you're working on a document, the parent program unexpectedly crashes and your work is gone. If you've setup a backup to run in the background, you'll be able to restore to the last backup point. |
| · | Your computer suffers a catastrophic failure, and you cannot access any files or folders. Having backed up onto an external drive or disk, you will be able to easily restore your valuable files onto a new computer. |
A restore operation swaps the source and destination directories: i.e. the source directory becomes the destination directory and visa-versa:
Usage: You have inadvertently deleted the wrong files. You quickly restore your files from an external hard drive back onto your main computer, then continue to work with little impact on your time or overall stress levels.
Usage: Your main computer suffers a serious security attack and your document files have been badly affected. After reinstalling Windows you are able to also restore your valuable document files to the state they were prior to the attack.
|
Note that a restore may not work in the way you expect it to: e.g. some of the files in the destination directory may be older than their equivalent entries in the source, and therefore may not replace the source entries (depending upon what your settings are).
If in doubt use the 'Simulated Run' feature in SyncBackSE. A simulated run will show you what will happen to your files, without actually copying, moving, or deleting files.
Running a restore operation is not reversible. |
All Content: 2BrightSparks Pte Ltd ⌐ 2003-2006